-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Conversation
Thanks @keitwb for this PR. This PR requires revisions, either because it fails to build or by reviewer request. Please make the suggested revisions. When you are done, please comment with text 'ready_for_review' and we will put this PR back into review. [This message brought to you by your friendly Ansibull-bot.] |
|
||
def main(): | ||
argument_spec = dict( | ||
network_name = dict(type='str', required=True), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs aliases=['name']
Overall this is looking good. If you can correct the minor things I pointed out, I think we can get this merged. Nice job! |
Thanks, I cranked the required docker-py version requirement up to 1.7+ since that is when they added the ipam support when creating a network. |
@chouseknecht I realized that this module doesn't allow for any easy way to disconnect containers from an existing network without having to specify all of the containers in the network. For example, removing a container from the default bridge network after having added it to a user-defined network. I was thinking the simplest way to do this would be to have a |
|
||
state: | ||
description: | ||
- < |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think you want > here and in other spots
@keitwb - we reviewed this today in the community meeting, New Module Review. Here are notes on required updates before this module can be accepted.
|
@keitwb A friendly reminder: this pull request has been marked as needing your action. If you still believe that this PR applies, and you intend to address the issues with this PR, just let us know in the PR itself and we will keep it open pending your changes. When you do address the issues, please respond with ready_for_review in your comment, so that we can notify the maintainer. [This message brought to you by your friendly Ansibull-bot.] |
@chouseknecht I did the change for the empty/null |
@keitwb Another friendly reminder: this pull request has been marked as needing your action. If you still believe that this PR applies, and you intend to address the issues with this PR, just let us know in the PR itself and we will keep it open. If you have addressed the issues and believe it's ready for review, please comment with the text "ready_for_review". If we don't hear from you within another 14 days, we will close this pull request. [This message brought to you by your friendly Ansibull-bot.] |
ready_for_review |
Thanks @keitwb for this new module. When this module receives 'shipit' comments from two community members and any 'needs_revision' comments have been resolved, we will mark for inclusion. [This message brought to you by your friendly Ansibull-bot.] |
Thanks @keitwb for this PR. Unfortunately, it is not mergeable in its current state due to merge conflicts. Please rebase your PR. When you are done, please comment with text 'ready_for_review' and we will put this PR back into review. For help on how to do this cleanly please see http://docs.ansible.com/ansible/community.html#contributing-code-features-or-bugfixes [This message brought to you by your friendly Ansibull-bot.] |
An updated version of this was merged in #4404 so I'm closing this. |
ISSUE TYPE
COMPONENT NAME
docker_network
ANSIBLE VERSION
SUMMARY
Implementation of https://github.com/ansible/proposals/blob/master/docker/docker_network.md